Job Coverage, step Generate coverage on 106a83b wanted to post the following:

Framework coverage

Diff coverage report

Full coverage report

Modules coverage

Coverage did not change

Full coverage reports

This comment will be updated on new commits.

Can someone pass judgement on including a test on this @GiudGiud @loganharbour @pbehne ? The simplest is a header() in MooseTestApp like 9e54f63

Can someone pass judgement on including a test on this @GiudGiud @loganharbour @pbehne ? The simplest is a header() in MooseTestApp like 9e54f63

I think we should just make another dummy app for it so that we don't get a header in every moose_test-opt run

Could also put a header in MiscApp

Could also put a header in MiscApp

I don't like testing framework content outside of the framework. misc testing doesn't contribute to framework coverage for example.

If we don't want another app, we can just do something silly like --test-set-header="foo" in MooseTestApp and then have header() return that result. So the header only shows up when we set it to. Goofy cause we'll basically have

--suppress-header --test-set-header="foo"

but we've done worse.

Job Documentation, step Docs: sync website on 106a83b wanted to post the following:

View the site here

This comment will be updated on new commits.

--test-set-header="foo"

Nice! I like this option! I kinda need the fix for setGlobalCommandLineParam @loganharbour is working on to cascade to all subapp levels first to do it right, but I'll whip something up before that fix is done.

Pretty easy to put

  params.addCommandLineParam<std::string>(
      "append_header", "--append_header <header>", "String to print at top of console output");

in MooseApp.C too for someone that may want that optoin...any reason to or just leave it in MooseTestApp.C?

It's not very useful imo

This works for cascading to subapps @loganharbour ...maybe that previous fix you suggested did work 😬